Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't propagate parent's context for the background replay #1219

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

mateusz-sekara
Copy link
Contributor

@mateusz-sekara mateusz-sekara commented Jul 24, 2024

Solution

It adds the missing part to this PR #1201

We can't pass the foreground routine context to the task run in the background and could take minutes or hours to finish. Instead of that, we create a background context and expose cancelFn. This is exactly how it used to work before introducing loopp layer

@cl-sonarqube-production
Copy link

@mateusz-sekara mateusz-sekara changed the title Test proper background replay Don't propagate parent's context for the background replay Jul 24, 2024
@mateusz-sekara mateusz-sekara marked this pull request as ready for review July 24, 2024 14:07
@mateusz-sekara mateusz-sekara requested a review from a team as a code owner July 24, 2024 14:07
@mateusz-sekara mateusz-sekara requested a review from a team July 24, 2024 14:20
@mateusz-sekara mateusz-sekara merged commit 52cdc60 into ccip-develop Jul 24, 2024
110 checks passed
@mateusz-sekara mateusz-sekara deleted the msekara/test branch July 24, 2024 14:24
asoliman92 pushed a commit that referenced this pull request Jul 31, 2024
## Solution

It adds the missing part to this PR
#1201

We can't pass the foreground routine context to the task run in the
background and could take minutes or hours to finish. Instead of that,
we create a background context and expose cancelFn. This is exactly how
it used to work before introducing loopp layer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants